The first thing is whether people can overcome their own preconceived notions. Do you need to see people to know they are working?

By opening the APIs, we're first beginning to realize the potential that different applications can bring to each other way beyond the core application. They develop it as a palette, and allow others to develop on that palette.

Before you consider how to deal with these issues on an individual worker level, you've got to first step back and look higher, and ask managers if they know what it means to manage knowledge workers, ... Our mental image of efficiency is rooted in the factory scene from Charlie Chaplin's 'Modern Times,' and managers base performance on how many widgets fly out the door. But customers and raw information aren't widgets, and you can't expect to handle them according to schedule.

Clearly, most of the time we're not talking about spending 2.1 hours on IM or talking on the phone about non-critical matters,

It's hard to say what will be next, but I have no doubt there will be other companies that have showstoppers.

It's not only technology, it's how knowledge workers behave. Companies have to recognize we're now dealing with a different type of work force, with significant changes. Quite honestly, there has been a very poor job done educating the business world about managing knowledge workers.

It's a very tough tightrope to balance oneself on. Everything could be the next important emergency that needs to be taken care of.

It's just mind boggling. All manufacturers have been aware that this is an ongoing problem that they have to watch for, so why they are unable to anticipate this type of problem is incomprehensible from an engineering standpoint.

This is not the first time that we've seen overheating batteries or power supplies. It seems that the attention that should be paid to these details is not paid.

Any challenger to a market where one player holds 80 percent share not only has to build a better mousetrap but improve upon the mouse.